Print

The latest release documentation of the Forms module.

1.  Release History

December 5, 2006

Forms module v5.2.3 is released.

Changes:

• New Feature: The relative path can now be used in the Access database settings.
  
• Fixed: No confirm on close with the Forms Module.
  
• Fixed: The error in the regular expression in the Forms Module.
  
• Fixed: The Forms Module resets the node's layout.
  
• Fixed: An error appears when saving a form without native default device.
  
• Fixed: The Forms error appears when trying to use the Field web control.
  
• Fixed: Click the Delete button in the Forms Editor Viewer and the dialog with only OK button appears.
  
• Fixed: The XSL rendering control provokes an exception.
  
• Fixed: Forms error appears when trying to use Field Web Control.

November 9, 2006

Forms module v5.2.2 is released.

Changes:

• Fixed: The Export to Excel button does not work.

August 28, 2006

Forms module version 5.2.1 is released.

Changes:

• Fixed: It is impossible to install the Forms module under Sitecore 5.1.1.19 with Firebird databases.
   
• Fixed: the Forms module crashes when performing the following scenario: Create a label on a form » Edit the text in the label » Hit enter to make the text more than one line » Click save.
   
• Fixed: The installation of Forms module causes the time out exception.

February 10, 2006

Forms module version 5.1.1.8 is released.

December 05, 2005

Forms module version 5.1.0.1 is released.

Changes:

• Each function gets an option which defines whether it should fire on page validation error. Three options are implemented: AlwaysFire, FireOnValidated, FireOnNotValidated. To have backwards compatibility, the option will be set to AlwaysFire by default.

October 21, 2005

Forms module version 5.1 is released

2.  Known issues

The list of known issues present in the current version.

• An unexpected error shown below occurs when using the forms editor. The reason is the site wasn't added to the trusted site list.
  
  

  The Solution: Add the Sitecore site to your trusted site list. 

  The reason is that only trusted sites are allowed to redirect requests from within a modal dialog in IE6. Thus, Sitecore must be a trusted site. 

• Attributes are not saved when a form is being saved in the Forms Editor if the mouse cursor is located on the attribute editor. The Solution: Exit the attribute editor before saving a form.